2014-12-08 - 16236 - Break Fix - Invalid Characters in PO Number #BWMonitoring
Break Fix
16236 - Invalid Characters in PO Number
Problem Summary
There are invalid characters in the PO field coming into BW. This creates errors and stops the process chains causing everything to fall behind.
Admin Info
Purpose
|
Need to fix the Invalid characters in PO Number.
|
Requested by
|
Mark Harris
|
Issue Date
|
12-08-2014
|
Resolved by
|
Uday Kumar P
|
Resolved Date
|
12-16-2014
|
Document Status
|
Complete
|
Detailed Problem Description
While creation of the Sales Orders in ECC system, the user enters some characters in PO Number field which were valid in ECC, but when extracted into BW system these characters are not valid. Due to this BW process chains fail frequently with DSO activation error. The failure of the DSO activation can be rectified by manually editing them in PSA which is time consuming process causing the delay of further dependent loads & Reports. Please find below some examples of invalid chars:

Solution Analysis and Recommendations
This issue can be fixed in 3 ways:
1. By changing the PO Number with correct characters in ECC.
2. By allowing them in RSKC in BW(only 72 characters are permitted here).
3. By using the routines.
Resolution
By writing the logic at the field level using a Function module "SCP_REPLACE_STRANGE_CHARS" all the invalid characters are replaced by corresponding characters by looking into the code pages & all the invisible characters are replaced by period(.) symbol.
Release Information
None